Link system for establishing high speed network communications and file transfer between hosts using i/o device links

ABSTRACT

A High Speed Link System providing network and data transfer capabilities, implemented via standard input/output (I/O) device controllers, protocols, cables and components, to connect one or more Host computing systems, comprising a System, Apparatus and Method is claimed; and described in one or more embodiments. An illustrative embodiment of the invention connects two or more Host systems via USB 3.0 ports and cables, establishing Network, Control, Data Exchange, and Power management required to route and transfer data at high speeds, as well as resource sharing. A Link System established using USB 3.0 operates at the full 4.8 Gbps, eliminating losses inherent when translating to, or encapsulating within, a network protocol, such as the Internet Protocol. Method claimed herein describes how two or more connected Host systems, detect one another, and establish separate communication and data exchange bridges, wherein control sequences from the Hosts&#39; application direct the operation of the Apparatus.

FIELD OF THE INVENTION

The present application relates generally to the establishment of anetwork for communications and high speed file transfers between one ormore Host systems using bridged connections of standard high speedperipheral devices and cables; and having a preferred implementationthat leverages Universal Serial Bus (USB) peripheral cables and devicecomponents, to establish USB Host to Host and Host to multi-Hostnetworking and high speed file transfers.

BACKGROUND OF THE INVENTION

Peripheral communications protocols provide the ability to connectadditional electronic devices directly to the CPU of a Host system. Mostmodern peripheral communications protocols provide ultra-high speedconnections to ensure the transfer of data to meet the requirements ofmodern CPUs. Popular peripheral protocols include the Universal SerialBus (USB) and the Peripheral Component Interconnect (PCI) among others.USB is a globally accepted and widely used plug-and-play interface forperipheral devices such as digital cameras, scanners, printers, CompactDisc (CD) players, Digital Versatile Disc (DVD) players, as well asmodern game consoles, etc. USB connections continue to evolve, providingimprovements in high speed data transfer with power delivery. Tworecently released versions of the USB Specification introduced multipleadvantages over previous versions and other protocols, including fullduplex communications. USB version 3.0 (hereinafter “USB 3”) delivershigh speed data rates of 5 Gbps (Gigabits per second) and USB version3.1 (hereinafter “USB 3.1”) delivers 10 Gbps.

Peer to peer connections between Hosts using USB version 2.0(hereinafter “USB 2.0” or “USB 2”) employ a fixed Host to Host cablewith embedded specialized electronic components and dependent on variousprotocol conversions. The USB 2.0 Host to Host cable is, in reality, avirtual Ethernet cross-over cable or bridge device deployed using theUSB interface solely as the medium for interconnection to the Hostcomputers. As such, these cables require proprietary drivers and pairedapplication software running at both ends of the connection; thuscreating substantial throughput limitations as Internet Protocol (IP)packet processing and conversions are required at each Host to supportthe connection. As a result, despite an available 40 MBps throughputprovided by the USB 2.0 port interface, actual data transfer speeds dropto only 12 MBps. Linking additional Hosts via Ethernet connections,while possible, is not viable—each additional host significantlyincreases overhead requirements and overall performance sufferssignificantly.

A direct USB 3.0 Host to Host connection has similarly been releasedinto the market, employing the familiar method of using Ethernetcross-over cable to carry encapsulated USB 3.0 packets. Effective speedof the USB 3.0-to-Ethernet Host to Host cable using this method isreported to be approximately 40 MBps; a significant reduction from theavailable 480 MBps provided by the USB 3 specification. New USB 3specifications define the use of a direct link USB 3 Male-A to Male-ACrossover cable, which does not include the Vbus or Bus Powercontingent, designed primarily for connecting two Hosts for the purposesof diagnosis and other restricted uses.

BRIEF SUMMARY OF THE INVENTION

The present application discloses a method and apparatus forestablishing a Link System providing network communications and highspeed data transfer capabilities between two or more coupled Hostcomputers (hereinafter “Host” or “Host system” or USB Host system”)employing at least two standard peripheral connections, in bridgedconfiguration, creating a dedicated communication link and a dedicateddata link which, in combination, form a private network to independentlyexchange control and high speed data between the coupled Host systems.Implementations employing the USB 3.0 SuperSpeed protocol, provide fornetwork and file transfer speeds of 5 Gbps; similarly the use of USB 3.1Enhanced SuperSpeed protocol and components can achieve speeds of 10Gbps.

In using the apparatus, methods and system proposed herein, the Hostsystems, upon connection, may detect one another and establish a networklink consisting of several bridged paths for network, control, highspeed data transfer, and power may be established. The Host systems mayemploy one or more protocols providing detection, negotiation, link,service, flow direction, high speed data transfer management, and powermanagement.

In a preferred embodiment, a proposed system comprises a centrallylocated Link System with a standard USB 3 Type-A Male connector at eachend of a link cable extending from the Link System. The Link System maybe seen to serve as to couple the USB 3 Host ports by interconnecting orbridging the various opposing communications and high speed dataexchange paths in a network environment in which control sequences fromthe Host application interact with both the Link System and oppositeHost system. The Hosts, coupled through the intermediary Link System,negotiate and facilitate the selection of data paths and datadirectional flow; interface elements and provisions to accommodate Dataand File transportation are provided by native Host Operating Systemfunctionality.

According to an aspect of the present disclosure, there is provided amethod for transferring data over links established between a firstuniversal serial bus Host and a second universal serial bus Host,wherein the link includes a first path on a physical layer of aninterconnection architecture and a second path on the physical layer ofthe interconnection architecture. The method includes the firstuniversal serial bus Host transferring, across the first path, linkcontrols to the second universal serial bus Host and the first universalserial bus host transferring, across the second path, high speed data tothe second universal serial bus Host.

According to another aspect of the present disclosure, there is providedan apparatus for connecting a first Host and a second Host. Theapparatus includes a high speed data link over a data bridge, aswitching manager adapted to create temporary interconnections betweenthe first universal serial bus Host and the second universal serial busHost, a Network and Control Manager adapted to establish addressing andnetwork switching, a Data Control Manager to direct the Data Exchangemechanism to transact Data and File Transfers between the firstuniversal serial bus Host and the second universal serial bus Host and adetector to detect that a device has been coupled to the apparatus.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of aspects of the present application isto be derived from the detailed description provided herein and from theaccompanying drawings relating to some embodiments of the presentapplication, which, however, are not to be understood as limiting to thespecific embodiments as detailed, but are for the purposes ofillustration to help better explain and for clarity in understanding thepresent application. Reference will now be made, by way of example, tothe accompanying drawings which show example implementations; and inwhich:

FIG. 1a illustrates, in a schematic diagram, a USB Network Controller inaccordance with aspects of the present application;

FIG. 1b illustrates, in a schematic diagram, a USB I/O Device Controllerfor Network and Control Management in accordance with aspects of thepresent application;

FIG. 1c illustrates, in a schematic diagram, a USB I/O Device Controllerfor Data Management in accordance with aspects of the presentapplication;

FIG. 2 illustrates a Link System in which an example USB Host system isillustrated along with the USB Network Interface comprising a USBNetwork Controller of FIG. 1a in accordance with aspects of the presentapplication;

FIG. 3 illustrates a Link System as an alternative to the Link System ofFIG. 2 in accordance with aspects of the present application;

FIG. 4 illustrates a Link System as an alternative to the Link System ofFIG. 2 and the Link System of FIG. 3 in accordance with aspects of thepresent application;

FIG. 5 illustrates a Link System featuring two coupled USB Host systemseach with the USB Network Interface comprising a USB Network Controllerof FIG. 1a similar to that illustrated in FIG. 2, in accordance withaspects of the present application;

FIG. 6a illustrates a schematic of a further USB Link System, whereinthere is a mirrored network interface implementation having multiplecomponents common to each side in accordance with aspects of the presentapplication;

FIG. 6b illustrates a schematic of the operational flow of a further USBLink System, wherein two USB Host systems couple and engage in a HighSpeed File Transfer process in accordance with aspects of the presentapplication;

FIG. 7 illustrates a Link System featuring a plurality of Host Systemsin accordance with aspects of the present application;

FIG. 8 illustrates, in schematic form, a Link System featuring a numberof support elements that form a pair of USB Network Interfaces forcoupling a first USB Host system to a second USB Host system inaccordance with aspects of the present application;

FIG. 9 illustrates, in schematic form, a Link System featuring two ormore separate pathways for Data Transfer to and from a USB Network inaccordance with aspects of the present application; and

FIG. 10 illustrates, in schematic form, the elements and operation of anApplication used in conjunction with a Link System featuring couplingbetween a first USB Host and a second USB Host in accordance withaspects of the present application.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Aspects of the present application, in some embodiments, wherein theperipheral communications protocol, and supporting connectors, devicecontrollers, linking mechanism and components, are described inreference to an implementation of the USB protocol, may equally refer toanother peripheral communications protocol such as PCI, and itsderivatives, SCSI or other communications protocols designed for Host toDevice communications.

Aspects of the present application, in some embodiments, wherein Host issynonymous with Host system and USB Host, relate to USB Host to Host andHost to multi-Host communications and networking;

Aspects of the present application, in some embodiments, wherein USBNetwork Interface relates to USB Link System comprising of two or morecoupled USB Network interfaces for USB Host to Host and to USB Host tomulti-Host Link communications and networking.

Aspects of the present application, in some embodiments, wherein USBNetwork Interface relate to the latest version USB (USB 3) USB LinkSystem comprising of two or more coupled USB Network interfaces for USBHost to Host and to USB Host to multi-Host communications andnetworking.

Aspects of the present application, in some embodiments, relate to USBHost-to-Host Link System and/or Bridge and/or Switch andHost-to-multi-Host Link System, and/or multi-Host Bridge and/ormulti-Host Switch.

Aspects of the present application, in some embodiments, relate to asystem wherein two or more USB Network Interfaces are coupled and form aLink System wherein links are formed and/or established.

Aspects of the present application, in some embodiments, relate to asystem wherein two or more Host systems are coupled by and/or through aLink System and links and or bridges are formed and/or established.

Aspects of the present application, in some embodiments, relate to asystem wherein two or more USB Network Interfaces are coupled and form aLink System wherein a Link System includes several individual links tothe first Host, and several other individual links to a second Host toform links or bridges between the Hosts and/or USB Network Interfaceswhen coupled.

Aspects of the present application, in some embodiments, relate to asystem wherein two or more Host systems (computers) are coupled byand/or through a Link System wherein a Link System includes severalindividual links to the first Host, and several other individual linksto a second Host and/or other Hosts to form links or bridges between theHosts systems when coupled.

Aspects of the present application, in some embodiments, relate to asystem wherein two or more Host systems are coupled by and/or through aLink System wherein a Link System includes several individual links toeach of several hosts in which various links or bridges are formedbetween any two or more coupled hosts, in a multi-bridge or data switchconfiguration.

Aspects of the present application, in some embodiments, relate to asystem wherein a bridge or data switch configuration provides forcommunications between any two coupled hosts, and separately andsimultaneously between any two other coupled hosts, in that multipleindividual bridges or linked data paths can be established ad hoc.

Aspects of the present application, in some embodiments, relate to asystem wherein a bridge or data switch configuration provides forcommunications and networking between any two or more coupled hosts, andseparately and simultaneously between any two or more other coupledhosts, in that multiple individual multi-host bridges or linked datapaths can be established ad hoc.

Aspects of the present application, in some embodiments, relate to asystem wherein a bridge or data switch configuration provides forcommunications and networking between any host to be bridged with anynumber of other coupled Hosts at the same time in a one-to-many Hostconfiguration or a broadcast type configuration.

Aspects of the present application, in some embodiments, relate to asystem wherein a bridge or data switch configuration provides forcommunications and networking between any number of coupled hosts to besimultaneously bridged with any one coupled Host at the same time in amany-to-one Host configuration or convergence-type configuration.

Aspects of the present application, in some embodiments, relate to asystem wherein a bridge or data switch configuration includes andsupports port-to-port and port-to-multiport and or Host to Host and Hostto multi-Host configurations providing direct, any-to-any, one-to-many,many-to-one, one-to-cascaded-many, one-to-any in hunt group, third-partycoupling, and expansion to additional parallel or daisy-chained LinkSystems.

Aspects of the present application, in some embodiments, relate to asystem wherein a bridge or data switch configuration in router modeprovides a means to link coupled Hosts belonging to one separate anddistinct network with coupled Hosts belonging to another separate anddistinct network.

Aspects of the present application, in some embodiments, relate to asystem wherein a bridge or data switch configuration in router modeprovides a means to link coupled Hosts belonging to one separate anddistinct network or virtual network with coupled Hosts belonging toanother separate and distinct network or virtual network.

Aspects of the present application, in some embodiments, relate to asystem wherein a system includes a first Host and a second Host. Thefirst host, upon being connected, detects the Link System and aconnection is established. The second host, upon being connected,detects the Link System and a second connection with the Link System isestablished, after which a bridge connection through the Link System isestablished, and thereby coupling or connecting the first Host with thesecond Host. Indeed, many more than just the first Host and the secondHost may be connected in this manner.

Aspects of the present application, in some embodiments, relate to asystem wherein a system includes a first Host system, a second Hostsystem, and a Link System. The Link System includes a detector to detectthe established connection to the first and second Host systems and theLink System logic establishes two or more bridge connections from thefirst Host system to the second Host system through the Link System.Indeed, many more than just the first Host system and the second Hostsystem may be connected in this manner, with potential for multiple Hostsystems, multiple Link Systems and multiple bridges.

Aspects of the present application, in some embodiments, relate to asystem wherein a system includes a first Host system, a second Hostsystem, a Link System, a coupling condition, and a virtual network. TheHost systems include a detector to detect the coupling condition throughthe Link System, and the Host logic establishes a virtual networkconnection or bridge to the second Host system as a response to thedetection condition. Indeed, many more than just the first Host systemand the second Host system may be connected in this manner, withpotential for multiple Host systems, multiple Link Systems, multiplecoupling conditions and multiple virtual network, network connections orbridges.

Aspects of the present application establish a method for transferringdata between two or more coupled Host systems; wherein a Link Systememployed comprises two or more separate and distinct paths on thephysical layer of an interconnection architecture; wherein theestablished paths are wired, wireless, virtual, or a combination ofsame; wherein high speed data is transferred between Host systems acrossenumerated Universal Serial Bus channels, and wherein network and linkcontrols are provided via one or more secondary or other, alternatecommunications path or paths on the same bridged link, separate from thepath or paths establishing other bridged links for high speed datacommunications.

In some embodiments, wherein a Host system coupled via a Link System isdetected, two or more ports or Host controllers of the detected Hostsystem are negotiated with, and it is determined whether to operate withthe detected Host system in response to the negotiating. Notably, thetwo or more ports or Host controllers may comprise one or moreendpoints.

In some embodiments, Host logic allows operation as a Host system andwith a coupled Host system, and a detector detects a coupled Host systemvia Link logic and determines whether to operate with the detected Hostsystem and the Host logic on the detected host responds to the Linklogic; and wherein Host logic resides on the Host systems and Link logicresides on the Link System. Notably, there may be multiple Hosts systemsand potentially multiple Link Systems.

In some embodiments, a cable device assembly or Link System couples afirst Host system and a second Host system. The second Host systemincludes Host logic to allow operation as a Host system, and a detectorto detect a coupled cable device assembly or Link System, and toindicate whether the Host logic is to be coupled to the cable deviceassembly or Link System. Indeed, many more than just the first Hostsystem and the second Host system may be connected in this manner.

In some embodiments, a coupling condition of a cable device assembly orLink System is detected, and an indication as to whether to couple withthe attached Host system or Host systems is made in response to thedetecting.

In an aspect of the present application, wherein more than two USB Hostsystems require coupling, the Link System takes on the role of a USBData Bridge or USB Data Switch in terms of configuration, wherebycoupled USB Host systems are interconnected through a series of Links ona main USB Network Bus or Buses; through the interconnection of a seriesof Links and or Buses, a basic configuration of the Link System may beexpanded in many aspects.

In some embodiments, multiple USB Host systems are coupled byimplementing multiple Link Systems between USB Host systems in adaisy-chain configuration wherein all USB Host systems, except thoselocated at the ends of the chain, employ an additional USB HostController and additional USB ports. The additional USB Host Controllersmay serve as an extension or bridge to the other separate Link Systemsin coupling adjacent USB Host systems to both the network and the datalinks and facilities.

In some embodiments, multiple USB Host systems are coupled by deployinga number of separate Link Systems to a centrally located USB Hostsystem, wherein a number of USB Host Controllers and USB ports aredeployed, to establish a star configuration wherein all coupled USB Hostsystems are interconnected in a Server-Client environment in which thecentrally located Host system emulates the aforementioned bridge/dataswitch configuration.

In some cases, according to aspects of the present application, multipleUSB Host systems are connected via a mix of daisy-chain, star, mesh andbridge/data switch interconnect configurations; in this manner,elaborate network structures can be created and implemented in eitherfixed or ad hoc installations.

In some embodiments, a dedicated hardware-based implementation may bemade, for example, in file sync applications. For example, in someembodiments, a personal computer or a Home Entertainment System canconnect to a notebook computer or tablet system using a USB Type-A toUSB Type-A cable with an embedded Link System for fast connection speedsand transfer of data and/or information.

Some aspects of the present application may allow a device with aconnection to a USB Host system to “push” data in controlled situations,particularly when the data is stored as a large file, as is common tomedia applications, wherein a user connects to a Host to rent orpurchase movies, video, music, documents, and/or other media, etc. Forexample, in some embodiments, distribution of music and/or videodownloads (for example, interactive DVD, HD-DVD, Blu Ray, etc.) at highspeeds (for example, USB 3 speeds) via kiosk type implementations, formedia retailing in locations such as airports, convenience stores, etc.

In some embodiments, a USB 3 Host system may appear to be and mayoperate as a USB 3 device and may enable what would appear to be a Hostto Host connection to be made, such that the coupled USB 3 Host systembecomes transparent to a user. In some embodiments, standard features(systems included as part of the Host system OS), such as a USB massstorage device driver, a device letter, and/or a file drag and dropfeature, may be used in either Command Line Interface or in GraphicalUser Interface to provide a means by which content can be moved orcopied between two USB Host systems. Additional user intervention insuch applications would not be required in conjunction with the use ofthese standard features, thereby allowing seamless operation forfeatures such as Sync-and-Go, or scheduled backups.

In some embodiments, a file transfer may be initialized and controlledby a storage facility that acts as a USB Host system, that supports twoor more coupled USB Hosts systems, and that may serve as a means toaugment a current local area network and/or a file storage facilityand/or a file sharing facility. For example, a file transfer may beinitialized and controlled by a network storage device in a user's hometo bridge fixed-place devices and portable devices, and/or as a filesync facility for daily document management in commercial applications.

Aspects of the present application may cause two or more servers toconnect; wherein each connected Host system (server) remains fullyoperational and able to control operations on other Host systems,including, but not limited to, file transfer, virus invigilation, otherfile processing or operations.

In some aspects of the present application, a Host to Host connectionsupports the provisioning of a shared environment such as a virtual hostor other sharing of system resources including but not limited to otherattached USB Devices and other network attached devices (for example aUSB thumb drive, or a Network Attached Storage unit (NAS).

In a particular embodiment, a USB Host system, usually a smaller systemsuch as a mobile phone, tablet or similar, may be provided with a dock,or similar resting point, may employ aspects of the present applicationto cause the establishment of a network connection to other USB Hostsystems, and/or devices. Connecting using aspects of the presentapplication may be considered to support sync-n-go, system resourcesharing, sharing of hardware features such as touch interfaces, andother components, whether implemented automatically at connection, orvia user control.

Some aspects of the present application may employ USB 3.0 or USB 3.1Host systems. In other aspects, other USB versions, such as USB 2.0, canbe used to provide same or similar performance. Future versions and/orimplementations are contemplated, using USB and/or other high speed orfast bus implementations and protocols.

While some embodiments have been described with regards to particularimplementations, in accordance with some or other embodiments, otherimplementations are possible. In addition, the order, composition and/orformat of components, circuit elements or other features represented inthe drawings and/or described herein are not necessarily required to bearranged in the particular way as represented or described herein.According to some embodiments, other arrangements are possible.

Terms such as “coupled” and “connected” used herein, may be replaced byany derivative such as “bridged.” Although seemingly having a similarcontextual definition, these terms are not intended as interchangeablereplacements for one another. More specifically, in particularembodiments, “connected” may be used to indicate that two or moreentities and/or elements and/or units are in direct physical orelectrical contact with each other, wherein “Coupled” and/or “Bridged”may mean that two or more entities are in direct physical or electricalcontact; and where “Coupled” and/or “Bridged” may also mean that two ormore entities and/or elements and/or units are not in direct contactwith each other, but exist and/or interact in a co-operative bind witheach other.

Terms such as “block” and “unit” are used herein, may be replaced by anyderivative such as “element.” Although seemingly having a similarcontextual definition, these terms are not intended as interchangeablereplacements for one another. More specifically, in particularembodiments, “block” may be used to indicate that two or more entitiesand/or elements and/or units are in relation to one another, wherein“unit” may mean two or more entities and/or elements and/or units are inrelation to one another and that two or more entities and/or elementsand/or units are not in relation to one another other, but exist and/orinteract in a co-operative bind with each other.

Some aspects of the present application may be implemented in one or anycombination of hardware, firmware, and software. Some embodiments mayemploy a computing platform to perform the operations described hereinwhereby instructions may be read and executed after having being storedon a machine-readable medium. Machine-readable media may include anymechanism that can store and/or transmit information in a form readableby a machine (for example, a computer). For example, a machine-readablemedium may include one or more of the following: read-only memory (ROM);random-access memory (RAM); magnetic disk storage media; optical storagemedia; flash memory devices; electrical, optical, acoustical or otherform of propagated signals (for example carrier waves, infrared signals,digital signals, the interfaces that transmit and/or receive signals,etc.), and others.

Accordingly, while some diagrams may have been used herein to describeparticular embodiments and/or implementations thereof, the presentapplication is not intended to be limited to those diagrams and/or tocorresponding descriptions herein. That is to say, the indicatedmovement or direction of any process or connection need to be or neednot to be with or through each illustrated box or connection point orentity, or to be or not to be in exactly the same order as illustratedand described herein.

In some embodiments, a USB Host may be used to operate as a USB device,wherein the connection from one USB Host system to another USB Hostsystem coupled either directly through a Link System or by means of analternate Network system so as to allow what would appear to be aHost-to-Host connection established in a manner which may be transparentto a user. In some embodiments, standard features normally associatedwith those being provided by the Host system Operating System, includinginteraction with USB Devices using a USB mass storage device driver,device letter, and/or file drag and drop features, may be used to moveor copy content between two Host systems. Integration with thesestandard mechanisms allows existing applications such as Sync and Go towork seamlessly and without the requirement of any additional userintervention. This aspect of the present application can be consideredadvantageous in that system and peripheral resource sharing forapplications in consumer, commercial and industrial scopes areconsidered high value for all facets of connectivity and storagesolutions and for virtualization solutions.

Accordingly, while some embodiments are described herein as USB 3embodiments, other aspects of the present application may not requirethese particular implementations. For example, some implementationsrequire other USB embodiments such as USB 2.0 and, likewise, it is alsocontemplated that future or alternate versions and/or implementations ofUSB and/or other fast bus implementations such as PCI, and itsderivations, SCSI or others thereof, may be performed according to someaspects of the present application.

Accordingly, with regards to each system shown in a figure herein, theelements within the figure, in some cases, may each have a same or adifferent reference number, so as to suggest that the elementsrepresented could be similar, same and/or different. Notwithstanding, anelement may be flexible enough to have different implementations andremain working with some or all of the systems shown or describedherein. The various elements shown in the figures, may be the same ordifferent. Which one is referred to as a first element and which iscalled a second element is in some cases arbitrary.

Accordingly, to some embodiments, USB 3 provides additional featuresincluding a bus training sequence used to establish the communicationsbetween USB ports, as part of the response to detecting a connection.Upon initial connection of the aspects of the present application, thereis an exchange of information between the Host system controllers andLink System controllers as is the case whenever a USB device isconnected to a USB Host port (for example, a USB Scanner to a USB Hostor a USB Device to a USB Hub). Host system controllers will declarethemselves as downstream ports (as in the normal manner) and Link Systemcontrollers will declare themselves as upstream ports (in a mannersimilar to a USB Device). This allows the Host system at either end ofthe Link System to act as a Host while both are connected, seemingly, toeach other, although, physically through the Link System which appearsas USB Devices to each of the respective connected Host systems. In thismanner a USB 3 peer-to-peer connection is possible, and a full scalepeer-to-peer network is also possible.

In some aspects of the present application, USB implementations usedifferentially driven receive block logic as well as differentiallydriven transmit block logic at either end of a coupled Link System,whereby the Network Manager appoints opposite ends as either the senderor the receiver as per the user interface Application's request.Additionally, in some embodiments, a USB interconnect may include twomore differential pairs or multiple differential pairs which can be usedand in some embodiments are used, for link management (for exampleNetwork and Control Management) and/or other lower speed and bandwidthdata communications.

Accordingly, in some embodiments, since USB 3 is a dual simplexconnection that supports concurrent IN and OUT transactions, atransmitter and a receiver block logic may be included in a Host system,and therefore beneficial to have the same in the Link System as blocklogic such that communications for each individual host is performedseparately and simultaneously with the Link System whether or not a datatransfer is executing at the time.

Accordingly, in some aspects of the present application, two USB Hostsystems (for example, two USB 3 Host systems) can be connected and/orcoupled together via the Link System, wherein for example, in someembodiments, a personal computer (PC) configured as HTPC (Home TheaterPC) can be connected and/or coupled with a tablet computer (for example,an iPad™ from Apple Inc. of Cupertino, Calif.) via a USB connection. Insome embodiments, a high bandwidth connection is made between systemswherein it is ideal for transferring large media files in extremelyshort times. For example, such a high bandwidth connection is used forrapid transfers of large media files containing standard definition (SD)content and/or high definition (HD) content (for example, from apersonal computer to a notebook computer for later playback). In someembodiments, the high bandwidth connection does not require any specificor additional support from a specification (for example, from a USBspecification such as a USB 2.0 or a USB 3.0 specification). In someembodiments, the high bandwidth connection uses unmodified USB type-Areceptacles (for example, unmodified USB 3.0 type-A receptacles). Insome embodiments, the operation of the high bandwidth connection istransparent to the user. In some embodiments, existing USB device classdrivers may be used (for example, existing USB 3 device class drivers).In some embodiments, Host systems having ports with capability for sucha high bandwidth connection may connect to a Link System for such animplementation.

In some aspects the present application, aspects can be delivered in aproduct form that would match the benefits of a passive crossover cable(for example, passive USB crossover cable such as a passive USB 3.0crossover cable) and may be used for the purpose of connecting two Hostsystems with the desired intention to transfer data back and forthbetween the coupled Host systems. The user's perspective, would be oneof a seamless nature, in that the connection between two Host systems(for example coupled together by means of aspects of the presentapplication configured as a Link System) would simply work whenever thecable is plugged in to each Host system. Sync and Go applications basedon drive letter addressing, simply work. In the manner as described, thethroughput efficiency is very high in that the Link System is servingand communicating directly with only two Host systems; saving valuablebandwidth and Network Management resources as would occur if deployingover an IP based protocol.

In some embodiments, performing may be considered synonymous withappearing to act, such that one Host system may perform as a host andthe second Host system may perform as a device, and on command, one Hostsystem may alternate to performing as a device, while the second Hostsystem, in synchronized manner, may alternately perform as a host. Insome embodiments, two Hosts each act simultaneously as both a host and adevice. For example, a Host system can in some embodiments performsimultaneously as both a host and a device.

In some embodiments, performing may be considered synonymous withappearing to act, such that a device configured as a bridge cable,comprised of a Link System situated in between the USB Male-A to USBMale-A connectorized cables, coupling the Host systems, perform as wouldan entirely passive cable (for example, a crossover cable). In someembodiments, the control hierarchy (which is to say, which Host systemwill perform as the conventional host and which shall perform as theconventional device) may be established using, for example, hardwareand/or hardware controlled by software, at one or both of the coupledHost systems. In some embodiments, the host performing as the host andthe host performing as the device, can be dynamically swapped usinghardware and/or software and/or both, at one or both of the Hostsystems.

In some embodiments, performing may be considered synonymous withappearing to act, such that a device configured as the Host system maybe presented to the coupled Host system as a Mass Storage Device, and/orperforming as having a connection with a directly attached storagesubsystem, wherein storage capability is provided.

In some embodiments, performing may be considered synonymous withappearing to act, such that a device configured as the Host system maybe presented to the coupled Host system as an Ethernet emulation modecommunication device and/or interface, and/or performing as facilitatingthe establishment of network addressable access, and/or networkaddressable access to other network addressable devices such as anetwork attached storage (NAS) subsystem, wherein storage capability isprovided.

In some embodiments, performing may be considered synonymous withappearing to act, such that a device configured as the Host system maybe presented to the coupled Host system as a device. For example, insome embodiments, the coupled Host system performs as a storage harddisk drive (HDD) having an OS generated and/or recognizable and/orcompatible drive letter, just as it would see any other USB storagedevice such as a USB thumb drive, wherein the coupled Host systemrequires no additional hardware or software to participate in a peer topeer connection. Logic may be resident at the coupled Host systems andwithin the Link System therein.

In some embodiments, performing may be considered synonymous withappearing to act, such that a device configured as the Host system maybe presented to the coupled Host system like any other networkaddressable host or file server (for example, a computer), and from theperspective of the Host system the coupled Host system may be presentedlike any other network addressable host or file server (for example, acomputer). In some embodiments, the network interface may be generatedby software (for example, a device driver) on the Host system, andpresents the file system in the same manner as any direct attachednetwork host or file server, or network attached storage (NAS) system.The driver may optionally present only a subset of the file system (forexample, the user's “My Documents” directory).

In some embodiments, performing may be considered synonymous withappearing to act, the Link System may perform as if employing the USBover IP protocol, although not employing the USB over IP protocol, whichis known to have inherent large overhead issues affecting operationalfactors and transfer speeds. The present application is not intended tobe limited to or preclude implementations from including and/or usingsuch protocol either exclusively or inclusively as a supplementalprotocol for any desired or required design criteria.

Notably, much the same could be said about the Link System performing asif employing the “IP over USB” protocol, in that aspects of the presentapplication may involve performing as if employing the IP over USBprotocol and, although it is not being employed, it is understood thatimplementations are not limited to or precluded from being employed byaspects of the present application or from being included and/or usingsuch protocol either exclusively or inclusively as a supplementalprotocol for any desired or required design criteria.

Aspects of the present application may be considered to relate to a dualinterface, such that some aspects may be implemented physically as adevice, these aspect may then appear as a Host at the Application level,thereby provisioning a Virtualized Host system with the ability toconnect to devices and other Hosts, both physical and virtual.

Aspects of the present application provide an ability for any coupledHost system to connect to multiple separate and distinct Link Systems.As such, the number of separate and independent data links to one ormany other Host systems may be seen to increase, such that the aggregatehigh speed data transfer throughput is equal to the sum of all of thetransfer speed capability of each of the attached Link Systems. Forexample, if any one Host system is attached to any one other Hostsystem, using four separate and independent bridged peripheralconnection pairs supporting the data transfer, using a separate anddistinct Host controller for each of the attached bridged peripheralconnection pairs by both Host systems, whereby the average transferspeed on any one data link through a Link System is 400 MB/s, the totalpotential throughput in this implementation would approximate 1600 MB/s.Aspects of the present application may be seen to include facilities totransfer one file using all available data links, or multiple filessimultaneously using all available data links. Other facilities could beincluded to use any number of the available data links in this type ofembodiment, as “Send Only” data links, with all other data links set as“Receive Only” data links. Other functionality can be included to switchany data link function (i.e., “Send Only”) to any other data linkfunction in an ad hoc manner. Embodiments of a similar nature could beused whereby relaying or routing of data to more than one Host systemwould provide higher throughput for applications requiring real timeduplication or redundancy. This aspect of the application can beconsidered as advantageous in that high speed data transfers may beprovided for applications in consumer, commercial and industrial scopesat lower cost points than current competitive solutions.

Aspects of the present application provide for establishment of a LinkSystem deployed as a virtual Host system, such as that commonly deployedas a Zero Client, in which a virtual host is implemented via aMulti-Seat Host OS, System/application, in which the user interfaces,namely video, keyboard, mouse and audio functionality and facility aredelivered to the Link System by means of the existing USB interface, andthe required USB controllers are implemented within the Link System forsuch an embodiment. Interconnection to other Desktop or Smart DeviceHost systems via the USB interface to the Link System may provide aprivate and high speed personal network for file sync, backup, etc.Additionally, an embodiment having specific interfaces and deployed insuch a manner can be construed as a Docking Station for Smart Devicessuch as laptops, notepads, tablets, phablets, Smart Phones, etc.,whereby the user is provided a means to implement an additional andtypically larger display or screen, a more accommodating keyboard, mouseand audio devices. Provisioning to the home or corporate network canalso be established through the Link System, with options for local andfaster storage, and common or shared file storage, or for access tocloud based storage.

Aspects of the present application, in some embodiments, relate to asystem wherein a device bridge provides for direct logical access tosystem resources, including CPU, Memory and hard drive, as well asperipheral resources such as printers, scanners and other devices; andwherein direct access to system resources eliminates protocolconversions required by other network methods and protocols, such asEthernet. Connections established via a bridged hub connection mayfurther establish default pools of privately shared resources availableto any connected Host without user or system intervention. This aspectof the present application can be considered advantageous in that systemand peripheral resource sharing for applications in consumer, commercialand industrial scopes are valuable for virtualization and otherconnectivity solutions.

The described implementations herein of the present application areintended to be examples only, and when employing USB 3.1 version of theprotocol, any and or each of the USB connectors referenced herein may beimplemented as a USB 3.1 Type-C connectors.

The described implementations herein of the present application areintended to be examples only. Alterations, modifications and variationsmay be effected to the particular implementations by those skilled inthe art without departing from the scope of the application, which isdefined by the claims appended hereto.

FIG. 1a illustrates, in a schematic diagram, a USB Network Controller100 in accordance with aspects of the present application. Asillustrated, the USB Network Controller 100 may include at least two USBdifferential pair connections or ports 118 and 178 respectfully (forexample a USB 2 differential pair connection or port 118, or a USB3multi-differential pair connection or port 178) each of which iscommunicatively connected to USB I/O Device Controller #1 110 and USBI/O Device Controller #2 170 respectively, which provide a CommunicationLink 136 and a Data Link 134 respectively along with combined PowerLinks 138 with an optional separate external Power supply port 198; toestablish interconnection with one or more USB Host systems, and whereupon a Virtual Network 124 may be established upon coupling with one ormore USB Host systems. Each USB I/O Device Controller #1 110, and USBI/O Device Controller #2 170 is illustrated in FIGS. 1b and 1crespectively.

FIG. 1b illustrates, in a schematic diagram, a USB I/O Device Controller#1 110 in accordance with aspects of the present application. Asillustrated the USB I/O Device Controller #1 110 may include Network andControl Management 112, a USB Network Interface 114, and a PowerInterface 116. The Network and Control Management block 112 may becomprised of various elements; a Code Logic block 156, a Memory Block152, a Clock 154, each of which is communicatively connected to eachother and additionally to a Central Processing Unit 150 (hereinafter“CPU”) and also interfaces directly with the Serial I/O Bridge 158 inthe USB Network Interface block 114 and additionally with the PowerManager 162 of the Power Interface block 116. In accordance with aspectsof the present application the USB I/O Device Controller #1 110 mayestablish a Communication Link across the Network and Control Bus 136for coupling with the USB I/O Device Controller #1 110 of one or moreother USB Network Controllers 100. Additionally, a Power Bridge 160 mayprovide Vbus Power and or an optionally provided external power sourceto the shared Power Bus 138 via the Power Manager 162 as may be directedby the USB Host system application, should the need be presented. Thevarious elements of the USB I/O Device Controller #1 110 may furtherinclude the establishment of a connection to the Virtual Network 124which may be seen as a virtual connection and used as a real IP Networkformed between any or all of the coupled USB Host system(s) to any othercoupled USB Host system(s).

FIG. 1c illustrates, in a schematic diagram, a USB I/O Device Controller#2 170 in accordance with aspects of the present application. Asillustrated the USB I/O Device Controller #2 170 may include DataControl Management 172, a USB Network Interface 174, and a PowerInterface 176. The Data Control Management Block 172 may be comprised ofvarious elements; a Memory Block 182, a Clock 184, each of which iscommunicatively connected to each other and additionally to a CentralProcessing Unit 180 (hereinafter “CPU”) and interfacing with a CodeLogic Block 186 and an Optional Control Logic block 196, both of whichmay be located externally of the Data Control Management Block 172; andmay also interface directly with the Serial I/O Bridge 188 in the USBNetwork Interface block 174 and additionally with the Power Manager 192of the Power Interface block 176. In accordance with aspects of thepresent application the USB I/O Device Controller #2 170 may establish aData Link across the Data Bus 134 for coupling with the USB I/O DeviceController #2 170 of one or more USB Network Controllers 100.Additionally, a Power Bridge 190 may provide Vbus Power and oroptionally provided external power to the shared Power Bus 138 via thePower Manager 192 as directed by the USB Host system application, shouldthe need be presented. The various elements of the USB I/O DeviceController #2 170 may further include the establishment of an optionalconnection from the Optional Control Logic block 196, to establish aCommunication Link across the Network and Control Bus 136. One of themain features of the USB I/O Device Controller #2 170 is the ability toadapt or convert incoming USB 3 formatted data through the Serial I/OBridge 188, which may then be altered to suit Bit-Wide delivery optionsranging from 4 to 64 as directed by means of the Bit-Wide Data Exchange194. This conversion process may also be deployed in the oppositedirection such that Bit-Wide Data may be adapted or converted to USB 3format for compliance with the USB 3 protocol.

In operation, the USB Network Controller 100 may allow for a linkbetween a USB Host system and a USB Network Bus to be provisioned.Furthermore, the USB Network Controller 100 may be useful whenestablishing a non-standard USB communications architecture, permittingone Host system to be directly connected to another Host system intypical computer network topologies and interconnections. The USBDifferential Pair(s) Connections or ports #1 118, and #2 178 mayfacilitate interconnection with a standard USB Host system (for example,a computer system) via a standard USB or USB 3 cable. The Powerconnection 198 may facilitate an interconnection with a standardexternal power source as a means for more or supplemental power. TheLink System interface buses including Network and Control Bus 136, theData Bus 134, the Power Bus 138 may facilitate interconnections with theUSB Network Bus, other buses, routers, switches and other similar ordissimilar networks.

As is illustrated in FIG. 1 b, the Network and Control Management block112 may facilitate a means by which a connection management system maybe deployed to bridge USB Host system communications with the USBNetwork Interface, for the purpose of interconnecting with and to othercoupled USB Hosts systems through a Link System comprised of two or morecoupled USB Network Controllers 100. The Network and Control Managementblock 112, may function as a traffic manager, wherein variouscommunication paths physical and virtual are established when USB Hostsystems are coupled through the Link System with each communication pathhaving specific and distinct operating functions and processes.

The Network and Control Management block 112 may receive and issuecommands. Additionally, the Network and Control Management block 112 maydetect and negotiate with the various systems within the USB NetworkController system 100 and, externally, with a coupled USB Host system,the Link System and the optionally provisioned internal Console portwithin the Code Logic 156, and other coupled USB Hosts and/or devices.

The Data Control Management block 172 as shown in FIG. 1c may interactwith the Bit-Wide Data Exchange unit 194 may enable fast buscommunications for high speed data and file transfers with the LinkSystem, performing data direction selection and path routing andswitching; and executing data flow and data speed alterations asinstructed by the Data Control Management block 172, and incollaboration with the direction of the Network and Control Managementblock 112. The Data Interface unit 174 may accommodate transfers ofcommand and control instructions and data, but does so as a secondaryand/or simultaneous parallel service, thereby supplementing its mainservice which is specifically to provision USB and USB 3 high speed dataand file transfers. Aspects of the present application include separateand distinct paths within the USB Link System. The Link System Data Busmay be connected to the USB I/O Device Controller #2 170 to enable fast,efficient and directed data delivery to and from the USB NetworkInterfaces 100, since control and addressing functions may mainly beprovisioned by the USB I/O Device Controller #1 110 connected to theControl bus of the USB Network.

The Code Logic blocks 156 and 186 may be configured to store machinecode data for use by the Network and Control Management block 112 andthe Data Control Management block 172 relating to configuration, processexecution, and data path and handling instructions.

The Virtual Network block 124 may be established as a pseudo-ControlManager within the coupled USB Host systems wherein functional networkcommands are carried out in sync with those issued at the Link Systemlevel. Functional network commands relate to control sequencing andoperational functions provisioned by and through the Network and ControlManagement block 112, and the Data Management block 172, between coupledUSB Hosts systems, and transacted on the Link System, as directed by theNetwork and Control Management block 112, from user interaction at theUSB Host system(s) Application level.

Other aspects of the present application may include a pre-processorunit and/or a postprocessor unit and/or both, placed or located anywhereprior to the Bit-Wide Data Exchange unit 194 in the case of apre-processor and/or placed anywhere after the Bit-Wide Data Exchangeunit 194 in the case of a post-processor and/or a mix of both as perdesign criteria. For example a buffer, a multiplexer/demultiplexer(mux/demux), a serializer/deserializer (SERDES), a data converter, a bitconverter, a bit checker, etc. Notably, Fiber Optic Cable may beemployed as the USB Transmission Line, with a benefit of reducingdistance limitations as well as noise interference and signaldegradation typically associated with high speed bus transmissions overcopper-based cable.

FIG. 2 illustrates a Link System 200 in which two or more USB Hostsystems 210 may be coupled in a fully addressable and managed Networkarchitecture by deploying a USB Network Interface 212 over a shared USBNetwork Bus 218. An example USB Host system 210 is illustrated. The USBNetwork Interface 212, as a portion of the Link System, may provide amanner for the USB Host system 210 to connect to a USB Network Bus 218.

Aspects of the present application may include two or more network pathsfrom the USB Host system 210 through the USB Network Interface 212 tothe USB Network Bus 218. At least one of those connections may be aphysical connection and all others may be either physical or virtual, ora combination of both.

In the embodiment illustrated in FIG. 2, a primary physical connectionmay employ a USB Transmission line 216 (for example, a USB 3 Cableincluding several differential pairs) connecting a USB 3 Port 232 of theUSB Host system 210 (for example, a Computer) to a USB 3 Hub 244 (forexample a USB3 Hub Controller) through USB Connector 242 to each of theUSB and USB 3 I/O Device Controllers built into the USB NetworkController 100. The USB Host system 210 may include the necessaryphysical and logical components for data storage, retrieval, access, andtransfer duties. The components may include: an Operating System 234; aFile System 236; one or more Data Stores 238; an Application 240; a USB3 Host Controller 228, and a Virtual Network Interface Controller (NIC)230.

A USB Network Transmission line 214, which may be connected to the LinkSystem interface via USB Network Controller 100, and may include a firstLink to bridge a Network Bus and or a Control Bus for addressing,signaling, switching and routing signals and controls, and a second Linkto bridge a high speed Data Bus, and a third Link to bridge a VirtualNetwork Bus 124 for application interfacing at the Host system, and afourth Link to bridge a Power Bus for delivery to coupled Host systemsor bridged device controllers for low-power or battery powered Hostsystems, may connect the USB Network Interface 212 to the USB NetworkBus 218.

In aspects of the present application, reductions may be found indistance limitations of the physical interconnects between the USB Hostsystem 210 and the USB Network Bus 218. As can be seen in FIG. 2, theUSB Transmission line 216 may be connected to the USB Network Interface212. In some embodiments, Copper USB cables serving as the USBTransmission line 216 may be limited to specific length dimensions, sothat only minimal external and internal signal degradation may occur dueto interference and differential pair signal loss on the USBTransmission line 216.

As Power and Ground signals are inclusive in USB connections, some powerlevels may be affected over distances and may not be sufficient as apower source for the attached Link System 200. As such, an ExternalPower connection may be provided by way of the Power port 254.

In operation, the Application 240 may provide a user with means toperform data and file transfers by means of a network facility. In someembodiments, the network facility may be serviced by the Virtual NIC 230which provides typical Internet Protocol type network functionality withaddress and port interaction in accordance with the OS 234 andApplication 240 requirements.

In some aspects of the present application, the Virtual NIC 230 may beestablished when coupling the USB Host system 210 to the USB Network Bus218. The coupling may be accomplished via the USB 3 port of a USB 3 Hub244 (for example a USB3 Hub Controller) through to each of the USB andUSB 3 I/O Device Controllers of the USB Network Controller 100 and viathe USB Network Transmission line 214, which may be connected to theLink System interface or USB Network Bus 218. Upon coupling, the OS 234enumerates a Virtual NIC 230, and may configure and or establish an IPaddress and Port on the Virtual NIC 230 which may allow for theApplication 240 to interact with other coupled USB Host systems 210presenting IP addresses on the same family and subnet. The Applicationmay render command instructions and associated system queries of theFile System 236 with respect to the data in the Data Store 238, on boththe USB Host system 210 and of that of any other coupled USB Host system210. The Application 240 also renders typical file handling and filetransfer commands typically associated with modern day computing systemssuch as file storage listings, file directory listings, file copy, move,delete, rename, compare, sync, backup, restore, etc., within the USBHost system 210 and with or to any other coupled USB Host system 210.

The Application 240 may interact with the OS 234 of the USB Host system210 and any other coupled USB Host system 210 seemingly via the VirtualNIC 230, but all communications concerning network and controlinstructions and information are conducted on the communications bridgelinking coupled USB Network Interfaces 100 on the Network and ControlBus 136. All exchanges of Data from one USB Host system 210 to any othercoupled USB Host system 210 may transact via the data bridge linkingcoupled USB Network Interfaces 212 on the Data Bus 134, thus may allowfor high speed data transfers in either direction.

USB cable lengths are relatively and prohibitively short in comparisonto alternate network wiring solutions (for example CATS, CAT6, etc.); assuch, the USB Host system 210 may be caused, by cable length, to be inclose proximity to the USB Network Interface 212. Other inherentrestrictions can impede the working distance by which the USB NetworkTransmission Line 214 can be accommodated, ranging from number ofconductors, shielding requirements, and gauge and connector structure asthe primary sources.

Provisioning of Power, as in all implementations of USB interconnects,may be derived from the USB Host system through the USB Transmissionline 216 and, ultimately, via the USB port 242. In situations in whichadditional Power is required, optional internal or external powersources may be connected or applied through the Power port 254,connecting to the USB Network Controller 100 Power Connection 198 andthen managed by either Power Manager 162 and or 192 as directed by theNetwork and Control Management 112, such that all systems arefunctioning optimally and such that any USB Host systems' datainteractions are not subject to communication speed reductions.

FIG. 3 illustrates a Link System 300 as an alternative to the LinkSystem 200 of FIG. 2. In the Link System 300 of FIG. 3, a USB NetworkInterface add-in card 350 is illustrated as internally mounted inside aUSB Host system 310.

The USB Host system 310 has many of the same components as the USB Hostsystem 210 of FIG. 2, including an Operating System 334; a File System336; one or more Data Stores 338; an Application 340; a Virtual NIC 330;a USB 3 Host Controller 332, and a USB port 366.

The USB Network Interface add-in card 350 may have many of the samecomponents as the USB Network Interface 212 of FIG. 2. That is, the USBNetwork Interface add-in card 350 may include a USB port 362 (like theUSB port 242 of FIG. 2), a USB Hub Controller 352 and a USB NetworkController 100 (like the USB Network Interface 212 of FIG. 2) and aPower port 356 (like the Power port 254 of FIG. 2). The USB NetworkInterface add-in card 350 may be implemented as a typical add-inperipheral card. Example typical add-in peripheral cards include: anadapter card; an expansion card; an add-in Ethernet Network InterfaceCard; and an externally attached dongle or device.

The USB Host Controller 332 may allow the connection to the USB NetworkInterface add-in card 350 to connect to the USB Hub Controller 352 usingthe USB port 366 of the USB Host system 310, and the USB Port 362 of theUSB Network Interface Addin Card 350, via a USB transmission line 316.

A USB Network Transmission line 314, which may be connected to the USBNetwork Controller 100, may connect the USB Network Interface add-incard 350 to the USB Network 218 in a similar fashion as outlined in LinkSystem 200 in FIG. 2.

In operation, USB port detection, connection and enumeration by aneXtensible Host Controller Interface (xHCI) root host and/or an EnhancedHost Controller Interface (EHCI) root host within the USB HostController 332 may be handled by established USB specifications. Onceconnected and enumerated, the combination of the USB Host system 310 andthe USB Network add-in card 350 form the Link System 300. Power for theUSB Network add-in card 350 may be provisioned, by way of the Power port356, directly from an Expansion Bus of the USB Host system 310 and maybe managed internally by a Power Manager similar to the Power Manager162 and or the Power Manager 192, which was described earlier, inconjunction with a review of the components of the USB NetworkController 100 of FIG. 1a, 1b, and 1c . The physical interface from theUSB Host system 310 to the USB Network 218 may be implemented through aUSB Network Transmission Line 314 which, as described earlier, can bemade of various buses and also interfaces virtually with the USB Host310 by an established Virtual Network as described previously.

In some aspects of the present application, the Virtual NIC 330 may beestablished when coupling the USB Host system 310 to the USB Network218. Once coupled, the USB Network Interface 114 of FIG. 1b may bedetected within the Application 340, and the OS 334, may enumerate theI/O port and thereafter may enable the Virtual Network driver within theUSB Host system 310 which may auto configure with an IP address and mayprovide access to various ports and resources for network activities.Upon activation, the OS may bind the Virtual Network InterfaceController 330, and the Application 340 may assume IP based networkconnections with other coupled USB Host systems, specifically using theData Interface 174 in FIG. 1c for all Bulk Data exchanges with othercoupled USB System hosts 310 including File Transfers to leverage theUSB 3 5 Gps bandwidth enabling high speed data transfer in the range of400-450 MBps.

In some embodiments, as illustrated by FIG. 3, USB Network interfacingmay provide significant advantages for Host-to-Host implementationswherein Host systems may be in close proximity to one another, such asin office environments, library pods, and in Server rack installations.The increased speed and bandwidth that may be realized by implementing a5 Gbps USB Network, may be seen to improve the overall usage andcapability over other commonly used and inexpensive networkingsolutions. In some aspects of the present application, concurrent use ofexisting network connections and the proposed USB Network is a means bywhich data transfers, data syncs, and daily backups can be provisionedmore quickly, securely and efficiently.

FIG. 4 illustrates a Link System 400 as an alternative to the LinkSystem 200 of FIG. 2 and the Link System 300 of FIG. 3. In the LinkSystem 400 of FIG. 4, a USB Network Interface add-in card 450 isillustrated as internally mounted in a USB Host system 410.

The USB Host system 410 has many of the same components as the USB Hostsystem 210 of FIG. 2, including an Operating System 434; a File System436; one or more Data Stores 438; an Application 440; a Virtual NIC 430and a USB Host Controller 432.

The USB Network Interface add-in card 450 has many of the samecomponents as the USB Network Interface 212 of FIG. 2. That is, the USBNetwork Interface add-in card 450 may include a USB Hub Controller 452and a USB Network Controller 100 (like the USB Network Interface 212 ofFIG. 2) and a Power port 456 (like the Power port 254 of FIG. 2). TheUSB Network Interface add-in card 450 may be implemented as a typicaladd-in peripheral card. Example typical add-in peripheral cards include:an adapter card; an expansion card; an add-in Ethernet Network InterfaceCard; and an externally attached dongle or device.

The USB Network Interface add-in card 350 has many of the samecomponents as the USB Network Interface 212 of FIG. 2. That is, the USBNetwork Interface add-in card 350 may include a USB Hub Controller 452and a USB Network Controller 100 (like the USB Network Interface 212 ofFIG. 2) and a Power port 356 (like the Power port 254 of FIG. 2). TheUSB Network Interface add-in card 350 may be implemented as a typicaladd-in peripheral card. Example typical add-in peripheral cards include:an adapter card; an expansion card; an add-in Ethernet Network InterfaceCard; and an externally attached dongle or device.

The USB Network Interface add-in card 450 may have some componentsdistinct from the USB Network Interface 212 of FIG. 2 and from the USBNetwork Interface Add-in Card 350 of FIG. 3, including a USB 3 HostController 462.

The USB Network Controller add-in card 450 may have a direct connectionfrom the USB Host Controller 462 to the USB Network interface 454 by wayof an internal connection of an onboard USB Transmission line, therebyeliminating an external USB Transmission Line to couple the USB Host 410to the USB Network Interface 100 of the USB Network Controller add-incard 450.

The interface between the USB Network Interface add-in card 450 and theUSB Host system 410 may be generically, for example, a Host Expansion orPeripheral bus. The Peripheral bus may, for example, be a local buscompliant with the Peripheral Component Interconnect (PCI) Local Busstandard or the PCI Express (PCIe) standard. To facilitate such aninterface, the USB Host may include a PCI slot 464 and the USB NetworkInterface add-in card 450 may include a set 466 of PCI conductors.

Notably, the USB bus may be considered to be an extension of the knownPCI bus and/or the known PCIe bus within a given Host system. It iscommon place for modern-day processors to expose the PCI/PCIe bus to theoutside world by means of a protocol exchange, namely, a USB controller.The USB controller provides interconnection functionality with devicesand other Hosts which are equipped with ubiquitous USB interfacingderived from their own exposed PCI/PCIe buses by means of compatible USBcontrollers. Such interfaces allow for high speed data transfer and orexchange over greater distances than that specified by the PCI/PCIespecification and at much lower cost than PCI/PCIe controllerimplementations. Also, new processor designs include USB buses direct tothe CPU, thereby eliminating the need for an additional protocolexchange via an externally mounted controller. Embodiments of theinvention claimed may include any “high-speed bus-related protocol”establishing Host to Device communications, and typically, but notnecessarily, having a physical implementation employing differentialpairs to deliver signals (data) at the hardware level; and areapplicable protocols for use by aspects of the present application.

A USB Network Transmission line 414, which may be connected to the USBNetwork Controller 100, may connect the USB Network Interface add-incard 450 to the USB Network Bus 218.

As established, and in similar fashion as explained with regards to FIG.3, connection and enumeration within the USB Host Controller 462 arehandled according to USB specifications; and once connected andenumerated, the combination of the USB Host 410 and the embedded USBNetwork Controller add-in card 450 form the Link System 400.

Power for the Network Controller add-in card 450 may be provisioned, byway of the Power port 456, directly from an Expansion Bus of the USBHost 410 and may be managed internally by a Power Manager similar to thePower Manager 162 and or the Power Manager 192, which was describedearlier, in conjunction with a review of the components of the USBNetwork Controller 100 of FIG. 1 a, 1 b, and 1 c. The physical interfacefrom the USB Host system 410 to the USB Network 218 may be implementedthrough a USB Network Transmission Line 414 which, as described earlier,can be made of various buses and also interfaces virtually with the USBHost 410 by an established Virtual Network as described previously.

In some aspects of the present application, the Virtual NIC 430 may beestablished when coupling the USB Host system 410 to the USB Network218. Once coupled, the USB Network Interface 114 of FIG. 1b is detectedwithin the Application 440, and the OS 434, enumerates the I/O port andthereafter may enable the Virtual Network driver within the USB Hostsystem 410 which may auto configure with an IP address and may provideaccess to various ports and resources for network activities. Uponactivation, the OS may bind the Virtual Network Interface Controller430, and the Application 440 may assume IP based network connectionswith other coupled USB Host systems, specifically using the DataInterface 174 in FIG. 1c for all Bulk Data exchanges with other coupledUSB System hosts 410 including File Transfers to leverage the USB 3 5Gps bandwidth enabling high speed data transfer in the range of 400-450MBps.

FIG. 5 illustrates a Link System 500 featuring two Host systems, a firstUSB Host 210A and a second USB Host 210B, connected to each other bymeans of a Host-to-Host Cable implemented by deploying two USB NetworkInterfaces, a first USB Network Interface 212A and a second USB NetworkInterface 212B.

As previously outlined in FIG. 2, the first USB Host 210A includesvarious components for data and file transfer. The components mayinclude: an Operating System 240A (not shown); a File System 236A (notshown); one or more Data Stores 238A (not shown); an Application 240A(not shown); a USB Host Controller 228A; a USB 3 Port 232A; and aVirtual NIC 230A. Similarly, the second USB Host 510B includes variouscomponents for data and file transfer. The components may include: anOperating System 240B (not shown); a File System 236B (not shown); oneor more Data Stores 238B (not shown); an Application 240B (not shown); aUSB Host Controller 228B; a USB 3 Port 232B; and a Virtual NIC 230B.

The first USB Network Interface 212A may, much like the componentsreferenced earlier with respect to FIGS. 1 and 2, include a first USBNetwork Interface port 242A (not shown), a USB Hub Controller 244A (notshown), a USB Network Controller 100A (not shown), and a Power port 254A(not shown). Similarly, the second USB Network Interface 212B mayinclude a second USB Network Interface port 242B (not shown), a USB HubController 244B (not shown), a USB Network Controller 100B (not shown),and a Power port 254B (not shown).

In FIG. 5, a first USB Transmission line 216A connects a first host USBPort 232A of the first USB Host system 210A to the first USB NetworkInterface Port 242A (not shown) of the first USB Network Interface 212A.Similarly, a second USB Transmission line 216B connects a second hostUSB Port 232B of the second USB Host system 210B to the second USBNetwork Interface Port 210B (not shown) of the second USB NetworkInterface 212B.

A first USB Network Transmission line 214A, which may be connected to afirst USB Network Controller 100A (not shown), may connect the first USBNetwork Interface 212A to a USB Network 218. Similarly, a USB NetworkTransmission line 214B, which may be connected to a first USB NetworkController 100B (not shown), and may connect the second USB NetworkInterface 212B to the USB Network 218.

In the first USB Network Interface 212A, an External Power connectionmay be provided by way of the first Power port 254A (not shown).Similarly, in the second USB Network Interface 212B, an External Powerconnection may be provided by way of the second Power port 254B (notshown).

As illustrated in FIG. 5, some embodiments relate to Host-to-Hostconnections for the purpose of deploying a Personal Area Network betweenHost systems of commercial, consumer and personal use such as Tablets,Laptops, Desktop Computers, and other smart devices including Smartphones and personal media players. In such an embodiment, the “bridgecable” use and operation resembles that of a ubiquitous USB2 Data Synccable or an Easy Transfer Cable in which two host systems are coupledvia a USB2-to-Ethernet converter bridged to the opposite side viaanother USB2-to-Ethernet converter, with relevance to an Ethernetcross-over cable; but enjoying the full transmission capacity availableon the USB cable, unencumbered by Ethernet conversions, nor constrainedby encapsulating USB transmissions within an Ethernet connection. Thisembodiment may be configured to allow remote control of the Hostopposite, such that all resources, connections, interconnections,peripherals, devices, applications, and OS features and controls, aremade available and usable with or without a security feature.

In some embodiments, the first USB Host 210A may be coupled to thesecond USB Host 210B via the Link System 500 by means of physical USBNetwork Bus 218, and a Virtual Network 124 being deployed uponenumeration of the first USB Network Interface 212A to the first USBHost 210A and the second USB Network Interface 212B to the second USBHost 210B. A closed loop deployment, the two USB Network Interfaces212A, 212B are situated centrally and in opposition to one another,creating a USB Network architecture wherein USB connectivity may beprovided to the USB Hosts 210A, 210B via the USB Transmission Lines216A, 216B at either end of the Link System 500. Application software240A, 240B (not shown) loaded and executed within respective USB Hosts210A, 210B, using typical file management and utility softwareapplications, and using common OS features, either located on orpreviously added to, respective USB Hosts 210A, 210B, may provide ameans by which a user of either of the USB Hosts 210A, 210B, may move,copy, create, delete, and list the files (among other tasks andutilities) located on local and remote data stores 238A, 238B (notshown). In some embodiments, any system resource or capability residingin, or connected to, one USB Host system (for example USB Host system210A) is also made available to the other USB Host system (for exampleUSB Host system 210B.

In operation, links may be established through the Link System 500.These paths may be internal or external and may be physical or virtual.Conveniently, aspects of the present application may allow theApplication 240A (not shown) and 240B (not shown), executed on the firstUSB Host system 210A, to connect and/or interface directly with or toany of the established links, be they internal or external, physical orvirtual for which one or more coupled USB Host system (for example USBHost system 210B).

FIG. 5 also illustrates I/O encoders 510A, 520A, 510B and 520B mayoptionally be added as indicated, and may optionally be used in theoperation of the apparatus. The I/O Encoders may be located within adevice controller or without, and may encode raw data received by thedevice controller for transmission across the data bus, and may decodereceived data from across the bus for transmission to the devicecontroller as raw data. As an example, the I/O encoder 520A may belocated in between the USB I/O Device Controller #2A 170A and the USBNetwork Bus 218 for transmitting and receiving on the Data Bus 134A overthe USB Network Bus 218 to the coupled Data Bus 134B; wherein the I/Oencoder 520B located between USB Network Bus 218 and the USB I/O DeviceController #2B 170B having received the encoded data, may decode andsend as raw data to USB I/O Device Controller #2B 170B. I/O encoders510A and 510B may be located between USB I/O Controller #1A 110A and #1B110B respectively.

FIG. 6a illustrates a schematic of a further USB Link System 600,wherein there is a mirrored network interface implementation havingmultiple components common to each side, some of which have beendescribed previously herein. As illustrated in FIG. 6a , a first USBHost system 210A may have a first USB 3 Host Controller 228A, and afirst USB connector 232A, for example a USB 3 Type A Female connectorphysically coupled to a first USB mating connector 242A, for example aUSB 3 Type A Male connector which may be connected to an embedded firstUSB 3 Hub Controller 244A; which may have two or more sets ofdifferential pair transmission lines and may also have Powertransmission lines, in which all transmission lines may be forming aconnection from the first USB 3 Hub Controller 244A to the first USB 3Network Controller 100A. A second USB Host system 210B may have a secondUSB 3 Host Controller 228B, and a second USB connector 232B, for examplea USB 3 Type A Female connector physically coupled to a second USBmating connector 242B for example a USB 3 Type A Male connector whichmay be connected to an embedded second USB Hub Controller 244B; whichmay have two or more sets of differential pair transmission lines andmay also have Power transmission lines, in which all transmission linesmay be forming a connection from the second USB 3 Hub Controller 244B tothe second USB 3 Network Controller 100B.

The first USB 3 Network Controller 100A may be connected to a second USB3 Network Controller 100B via several USB Network Transmission Lines214A (not shown) coupled to other several USB Network Transmission Lines214B (not shown) forming a USB Network Bus 218 (not shown) illustratedas several independent segments coupling several independent processblocks and interfaces, 134, 136, 138, 124.

The first USB connector, for example a USB 3 Type A Male connector 626Amay connect to a first USB 3 Hub Controller 606A via two or more sets ofdifferential pair transmission lines and may also include Powertransmission lines (not shown).

Similarly, the second USB connector, for example a USB 3 Type A Maleconnector 242B may connect to a second USB 3 Hub Controller 244B via twoor more sets of differential pair transmission lines and may alsoinclude Power transmission lines (not shown).

The first USB 3 Hub Controller 244A may connect to a first Network andControl Management block 110A for example a USB I/O Device Controller#1, of the first USB 3 Network Controller 100A via two or more sets ofdifferential pair transmission lines and may also include Powertransmission lines 604A.

Similarly, the second USB 3 Hub Controller 244B may connect to a secondNetwork and Control Management block 110B for example a USB I/O DeviceController #1, of the second USB 3 Network Controller 100B via two ormore sets of differential pair transmission lines and may also includePower transmission lines 604B.

The first USB 3 Hub Controller 244A may also connect to a first DataControl Management block 170A for example a USB I/O Device Controller#2, of the first USB 3 Network Controller 100A via two or more sets ofdifferential pair transmission lines and may also include Powertransmission lines 612A.

Similarly, the second USB 3 Hub Controller 244B may also connect to asecond Data Control Management block 170B for example a USB I/O DeviceController #2, of the second USB 3 Network Controller 100B via two ormore sets of differential pair transmission lines and may also includePower transmission lines 612B.

The first USB 3 Hub Controller 244A may also connect to both the firstUSB I/O Device Controller #1 Power Manager 162A and to the first USB I/ODevice Controller #2 Power Manager 192A via two or more sets Powertransmission lines 608A.

Similarly, the second USB 3 Hub Controller 244B may also connect to boththe second USB I/O Device Controller #1 Power Manager 162B and to thesecond USB I/O Device Controller #2 Power Manager 192B via two or moresets Power transmission lines 608B.

The first Network and Control Management block 110A may be coupled tothe second Network and Control Management block 110B by a Network andControl Bus 136.

The first Power Management block 162A and 192A may be coupled to thesecond Power Management block 162B and 192B respectively, by a Power bus138.

The first Data Control Management block 170A may be coupled to thesecond Data Control Management block 170B by a Data Bus 134.

In some aspects of the present application, as illustrated in FIG. 6a ,I/O encoders 510A, 520A, 510B and 520B may optionally be added asindicated, and may optionally be used in the operation of the apparatus.The I/O Encoders, as previously described herein, may be located withina device controller or without, and may encode raw data received by thedevice controller for transmission across the data bus, and may decodereceived data from across the bus for transmission to the devicecontroller as raw data.

Each of the first transmission lines 604A, 608A and 612A and each of thesecond transmission lines 604B, 608B and 612B may be implemented as, forexample, copper traces on a circuit board or other embedded means withinthe Link System.

In operation, the various blocks 110A and 110B, 162A, 192A and 162B,192B, and 170A and 170B in combination with the corresponding buses 136,138 and 134 may be seen to form a USB Network which includes anestablished virtual network 124 having IP based addressing and usingvirtual Ports commonly associated with IP based networking. Physicalnetwork communications takes place over the Network and Control Buses136 in which USB I/O Device Controllers on either Network Controller100A and 100B communicate using a serial protocol. The protocol may beany of the industry standard and accepted serial communications protocolas interconnection of Transmit and Receive signaling may be arequirement. These commonly used protocol may include RS-232, RS-422,RS-485, SPI, I2C, CAN, etc. Physical Data exchange takes place over theData Buses 134 in which USB 3 I/O Device Controllers #2 on eitherNetwork Controller 100A and 100B transact Bulk Data Transfer overselected SuperSpeed Endpoints. Transfer methods such as Bulk Datatransfer, Asynchronous data transfer and Isochronous First-In-First-Out(FIFO) data transfer may be used for alternate forms of transfer such ascontinuous feed or Streaming Data. Different functions within anApplication may be directed to different endpoints. Each endpoint may beselected on the basis of the suitability of the endpoint to perform adesired function. Similarly, data traffic may be directed to an endpointthat is suited to an identified data speed when coupling differentversions of USB Hosts.

FIG. 6b illustrates a schematic of the operational flow of a further USBLink System, wherein two USB Host systems couple and engage in a HighSpeed File Transfer process in accordance with aspects of the presentapplication.

The Data Transfer process requires that Host 1, may connect to theapparatus, and may have all supporting devices and components enumeratedand may have established an IP address on the Virtual Network, maycouple with Host 2, which also may require being connected to theapparatus, and may have all supporting devices and components enumeratedand may have established an IP address on the Virtual Network. Host 1and Host 2 may now be connected via the Virtual Network and exchangeNetwork and Control Commands on the Physical Network and Control Bus.The primary interaction in the Data Transfer process is that Host 1 mayquery Host 2 for data listing such that the User receives informationregarding the Files and their locations on Host 2. Once decided by theUser, Host 1 may transmit via the Network and Control Bus endpoint aSend request to Host 2 such that a specific file, on Host 2, may betransferred. Host 2 may acknowledge and may create payload informationand may send to Host 1. Payload details may include file name, bytecount, and various security and checksum details. Host 2 may ready theBulk Transfer Endpoint on the Data Bus and endpoint may enter standbymode in anticipation of the Request to Send condition set by Host 1.Host 1 may select a Bulk Transfer Endpoint and may establish the spaceneeded for the incoming File. Host 1 may send to Host 2 a Request toSend on the Network and Control Bus. Host 2 may acknowledge the Requestto Send command, and may engage the Bulk Transfer process to send theselected File to the expectant endpoint on Host 1 via the high speedData Bus. Upon completion, Host 2 may close the Data Bus endpoints andmay reset back to normal operation. Host 1 may upon completion of theData Transfer, close the Data Bus endpoint and may assess the payloadagainst the payload information previously acquired, for payloadcompleteness, integrity and security. This process may continue torepeat itself should the User select numerous files or entire folders orentire Drive contents.

FIG. 7 illustrates a Link System 700 featuring a plurality of USB HostSystems 210. Each USB Host system 210 of the plurality of USB HostSystems 210 may be connected, via a respective USB Transmission Line216, to a USB Network Switch 706. The USB Network Switch 706 may also becalled a USB Network Router or a USB Network Bridge. At the USB NetworkSwitch 706, each of the USB Transmission Lines 216 may be received at arespective plurality of USB ports (not shown). Within the USB NetworkSwitch 706, a shared USB Network Bus 218 may be found. A plurality ofUSB Network Interfaces 212 may connect to the shared USB Network Bus 218via bi-directional USB Network Transmission Lines 214. Furthermore, eachof the plurality of USB Network Interfaces 212 may connect to arespective one of the USB ports 242 (not shown).

Conveniently, the USB Network Transmission Lines 718 are locatedinternal to the USB Network Switch 706.

The USB Network Switch 706 may include a Network Manager Interface 714connected to the shared USB Network Bus 218.

The USB Network Bus 218 may be seen to establish a central data and filetransfer distribution center for the plurality of USB Host systems 210,as is the case for most modern-day computer-based network systems suchas, for example, Ethernet Switches, Bridges and Routers. Since, the USBNetwork Bus 218 is internal to the USB Network Switch 706, it followsthat the Network and Control Bus and the Power Bus are internal to theUSB Network Switch 706. Accordingly, only the USB ports 242 (not shown)are exposed for coupling with the USB Host systems 210.

In operation according to some aspects of the present application, theNetwork Manager Interface 714 may provide enhanced and additionalcontrol at the Console level for internal system configuration,security, diagnostics, and administrative control. The Network ManagerInterface 714 may, additionally, be used to offset, or to supplement,the Network and Control Management of any or all of the USB NetworkInterfaces 212. Interaction with the internally located USB NetworkInterfaces 212 may be carried out through physical network pathways orvirtual network pathways. Furthermore, a given one of the USB Hostsystems 210 may facilitate communications with the Network ManagerInterface 714 based on administration, configuration and securitysettings and parameters, using a Network Manager Console application(not shown) on the given one of the USB Host systems 210.

In some aspects of the present application, as illustrated in FIG. 7,the number of USB Network Interfaces 212 is not limited by USBspecification or conventions, nor by other network architecturerestrictions or limitations. Indeed, theoretically, an unlimited numberof USB Network Interfaces 212 may be coupled or interconnected, eitherdirectly or through interconnections of differing topologies, whereinconcatenation of two or more USB Network Switches 706 is possible. Asmentioned hereinbefore, the USB Network Switches 706 may also be knownas Bridges and/or Routers.

In operation, through the coupling of the physical network components,including the USB Host systems 210, the USB Transmission Lines 216, theUSB ports 242 (not shown), the USB Network Transmission Lines 214 andthe USB Network Bus 218, a Virtual Network 124 may be seen to have beenestablished. Notably, the specified Network Switches, Bridges, and/orRouters can be provisioned and/or located internally or externally andin either, or both a physical or virtual presence. Also, the actuallocation of any Network Switch, Bridge or Router is not to be understoodas being only positioned as depicted in FIG. 7, but can be locatedanywhere it is deemed to be necessary.

It can be said that in accordance with the description of the elementsand components described earlier herein with respect to FIG. 2, similarelements having similar functionality in FIG. 7 may be established asbeing interchangeable.

In some aspects of the present application, as illustrated in FIG. 7, aUSB Host system 210 having interconnection with the Virtual Network 124through interconnection of Virtual Router or Bridge, may optionally beused as a Network Manager and have Remote access capabilities with theNetwork Manager 714 or with any coupled USB Host system 210 should thesystem be configured in such a manner to provide this type of access andusage.

FIG. 8 illustrates, in schematic form, a Link System 800 featuring anumber of support elements included in each of a pair of USB NetworkInterfaces 212A and 212B for coupling a first USB Host system 210A to asecond USB Host system 210B. The FIG. 8, in the configuration shown isnot inclusive of some of the components that are either being referredto and states as not shown, or are not indicated as their functionalityalthough pertinent to the overall function of the Link System is notincluded in the scope of this particular description of this or othersimilar embodiments, including USB 3 Hub Controllers, USB Connectors,and optional I/O encoders, etc.

The first USB Host System 210A may be coupled, via a first USB NetworkInterface 212A, to the second USB Host system 210B via a second USBNetwork Interface 212B. The USB Network interface 212A and 212B has beendescribed previously herein as it pertains to FIG. 2. The first USB Hostsystem 210A and the second USB Host system 210B, have also beendescribed previously herein pertaining to FIG. 2, and are not shown inFIG. 8 but are understood to be connected via the first USB Interconnect804A and a second USB Interconnect 804B, respectfully. The USB Hostsystems 210A and 210B (not shown) may each comprise a USB HostController; a USB Connector and a USB Transmission Line, describedearlier herein, inclusive of several differential pairs and ormulti-pairs and related Power conductors.

The first USB Network Interface 212A may include a first PowerManagement unit 842A. The second USB Network Interface 212B may includea second Power Management unit 842B. Both Power Management units 842Aand 842B may be comprised of the Power Interfaces 116 and 176 of each ofthe USB I/O Device Controller #1 and #2 within the USB NetworkController 100 as previously referenced herein. The first PowerManagement unit 842A may be connected to the second Power Managementunit 842B via a Power Bus Link 138A and 138B within the USB Network Bus218, in accordance with the controls and commands issued from andthrough the Application 240 (not shown) on any of the coupled USB Hostsystems.

The first USB Network Interface 212A may include a first USBDifferential Connection in which a first USB2 endpoint 834A and a firstUSB 3 endpoint 832A may be established. The second USB Network Interface212B may include a second USB Differential Connection in which a secondUSB2 endpoint 834B and a first USB 3 endpoint 832B may be established.The first endpoints 832A, 834A may be made to communicate with thesecond endpoints 832B, 834B respectively via a Data Bus Link 134A and134B within the USB Network Bus 218.

The first USB Network Interface 212A may further include a first PortDetector 822A which may connect to a first Link Negotiator 824A, whichmay be connected to a first Link Manager 826A. Similarly, the second USBNetwork Interface 212B may further include a second Port Detector 822Bwhich may connect to a second Link Negotiator 824B, which may connect toa second Link Manager 826B. Port Detector 822A and 822B and LinkNegotiator 824A and 824B may be directed by the user Application 240(not shown) and USB Host System OS 234 (not shown) as required.

Furthermore, a first USB Network Interface 212A may include a firstService Management Block 812A and the second USB Network Interface 212Bmay include a second Service Management Block 812B. The first ServiceManagement Block 812A and the second Service Management Block 812B maycommunicate via Service Bus Links 810A and 810B respectively as each aresegments of the Network and Control Bus 136A and 136B respectively, andmay be directed by the user Application 240 (not shown) and USB HostSystem OS 234 (not shown) as required.

The coupled Service Bus Links 136A and 136B may also be used when thefirst Service Management Block 812A and the second Service ManagementBlock 812B communicate directly. Furthermore, the first ServiceManagement Block 812A and the second Service Management Block 812B mayemploy an Addressing facility and may be directed by the userApplication 240 (not shown) and USB Host System OS 234 (not shown) asrequired.

FIG. 8 illustrates an embodiment of the present application wherein thefunction of the Power Management units 842A, 842B may provision andmonitor power requirements of the apparatus for optimal operation withrespect to use of the fastest bus; and according to various factors,including, but not limited to, the distance from a connecting USB HostSystem, and the capacity relating to the USB Host System Bus powercapacity when executing data transfer operations. Power may be derived,primarily, from a USB Host system through the appropriate USBInterconnect 804A, 804B. Within one or more embodiments, additionalpower may be provided via internal or external power courses, applied orconnected via additional Power interconnects such as, as an example, andexternal Power adapter. Alternatively, external power sources may beapplied or connected via any other coupled USB Host system on the PowerBus 138A and 138B, providing the other coupled USB Host system hassufficient regulated power and capacity. Furthermore, Power Managementunits 842A, 842B may be directed by the user Application 240 (not shown)and USB Host System OS 234 (not shown) as required.

In operation of the Link System 800 of FIG. 8, data may be passedbetween USB Host systems 210A and 210B using one of either the USB 2endpoints 834A, 834B or the USB 3 endpoints 832A, 832B. In either case,the data may be directed by a Data Control Manager to a Data Exchangeunit, such as found as the Data Control Manager 172 (not shown) and theData Exchange unit 194 in the USB Network Controller 100 of FIG. 1a andof the USB I/O Device Controller #2 in FIG. 1 c. Additionally, the datamay be reformatted and prepared for transfer to the Data Bus 134A and134B. A Data Control Manager, such as the Data Control Manager (notshown) in the USB Network Controller 100 of FIG. 1a and of the USB I/ODevice Controller #2 in FIG. 1 c, may provide an open path anddirectives to each USB Host system to engage the transfer process. Insome aspects of the present application, the Data Exchange unit 194 (notshown) may accommodate same and mixed transfers of any combination ofUSB 2 and USB 3 originating data and speeds. Optionally, Data I/Oencoders (/decoders) 510A, 510B, and 520A and 520B as describedpreviously herein with respect to FIG. 5, may be provisioned within thisembodiment as well.

FIG. 8 does not show a Network and Control Manager 112 (not shown).However, in consideration of the Network and Control Manager 112 of theUSB Network Controller 100 of FIG. 1a and 1 b, one may consider that, inoperation of the Link System 800 of FIG. 8, a Network and ControlManager 112 (not shown) synchronize, coordinate physicalinterconnections, and Virtual interconnections, between the coupled USBHost systems.

The Network and Control Manager 112 (not shown) may defer control to theApplication 240 (not shown) and OS 234 (not shown). Indeed, the Networkand Control Manager 112 (not shown) may attend, primarily, to lowerlevel functions concerning detection and negotiation of the connectedUSB endpoints and implementing address determination and selectionprotocols along with data direction and flow control for the coupled USBHost systems 210A and 210B.

In operation, the first Port Detector 822A may sense the USB connectiontype. Accordingly, the first Port Detector 822A may permit or declinethe connection as per Driver and Operating System 240A (not shown)instructions from one or more connected USB Host systems. If aconnection is permitted, the first Link Negotiator 824A may establish asuitable physical and/or virtual reference for the connected USB Hostsystem prior to being coupled with another USB Host system. The firstLink Manager 826A, in turn, may establish an address on the firstAddress Bus Link 136A. The first Link Manager 826A may also inform thefirst Network and Control Manager 112 (not shown) of the pairing ofphysical and/or virtual addresses for the USB Host System 210A and 210Band the USB Network Interfaces 212A and 212B.

The first Service Management Blocks 812A and 812B may provide additionalconsole-type connections for loading and upgrading code logic of the USBNetwork Interfaces 212A and 212B respectfully. The first ServiceManagement Block 812A may also provide non-essential services, includingcontrol and switching of external reporting mechanisms for Processconfirmations and/or acknowledgements of services. Exchange of suchservice to either side of the USB Network Bus 218 is provided for on theService Bus Links 136A and 136B, and may be managed by the Network andControl Manager 112A (not shown) using logic executed by the first LinkManager 826A.

Process confirmations may include error, power, security and/or modelevel indication and reporting. One example of a means to provideconfirmation in a preferred embodiment comprises Light Emitting Diodesignaling indicators using distinct colors to provide distinctindications or by on-off or dimming states.

FIG. 9 illustrates, in schematic form, a Link System 900 featuring twoor more separate links for a Data Link for Data and File Transfer and aCommunication Link for Network and Control communications to and from aUSB Network Bus 218. The Link System 900 of FIG. 9 includes a USB 3SuperSpeed configuration 902 and an alternative USB 2 Hi-Speedconfiguration 904.

The USB 3 SuperSpeed configuration 902 includes a first USB I/O DeviceController #2 910A connected to the USB Network Bus 218 via a firstplurality of USB Network Transmission Lines 912A. Additionally, thefirst USB I/O Device Controller #2 910A may be connected to a first USB3 Hub Controller 916A terminating to a USB 3 Male Type A connector 914Avia a first USB 3 Transmission Line 906A. The USB 3 SuperSpeedconfiguration 902 also includes a first USB I/O Device Controller #1920A connected to the USB Network Bus 218 via the first plurality of USBNetwork Transmission Lines 912A and may be connected to a first USB 3Hub Controller 916A also terminating to a USB 3 Male Type A connector914A via the USB 3 Transmission Line 906A. The target USB Host systemmay have a USB 3 Host Controller and USB 3 external Ports available forwhich to connect this configuration of the described embodiment in a USB3 SuperSpeed configuration.

The USB 3 SuperSpeed configuration 902 further includes a second USB I/ODevice Controller #2 910B connected to the USB Network Bus 908 via asecond plurality of USB Network Transmission Lines 912B. Additionally,the second USB I/O Device Controller #2 910B may be connected to asecond USB 3 Hub Controller 916B and terminating to a USB 3 Male Type Aconnector 914B via a second USB 3 Transmission Line 906B. The USB 3SuperSpeed configuration 902 also includes a second USB I/O DeviceController #1 920B connected to the USB Network Bus 908 via the secondplurality USB Network Transmission Lines 912B and may be connected tosecond USB 3 Hub Controller 916B and terminating to a USB 3 Male Type Aconnector 914B via a second USB 3 Transmission Line 906B. The target USBHost system, may have a USB 3 Host Controller and USB 3 external Portsavailable to connect, completes this configuration of the describedembodiment in a USB 3 SuperSpeed configuration.

The USB 2 Hi-Speed configuration 904 includes a first USB I/O DeviceController #2 910A in an alternative configuration connected to the USBNetwork Bus 218 via the first plurality of USB Network TransmissionLines 912A. Additionally, the first USB I/O Device Controller #2 910A inan alternative configuration may be connected to a first USB 3 HubController 916A and terminating to a USB 3 Male Type A connector 914Avia a first USB 3 Transmission Line 906A. The USB 2 Hi-Speedconfiguration 904 may also include a first USB I/O Device Controller #1920A connected to a first USB 3 Hub Controller 916A also terminating toa USB 3 Male Type A connector 914A via the USB 3 Transmission Line 906A.The target USB Host system may have only USB 2 Host Controller and USB 2external Ports available for which to connect this configuration of thedescribed embodiment in a USB 2 Hi-Speed configuration.

The USB 2 Hi-Speed configuration 904 further includes a second USB I/ODevice Controller #2 910B in an alternative configuration connected tothe USB Network Bus 218 via the first plurality of USB NetworkTransmission Lines 912B. Additionally, the second USB I/O DeviceController #2 910B in an alternative configuration may be connected to asecond USB 3 Hub Controller 916B and terminating to a USB 3 Male Type Aconnector 914B via a second USB 3 Transmission Line 906B. The USB 2Hi-Speed configuration 904 may also include a second USB I/O DeviceController #1 920B connected to a second USB 3 Hub Controller 916B alsoterminating to a USB 3 Male Type A connector 914B via the USB 3Transmission Line 906B. The target USB Host system may have only USB 2Host Controller and USB 2 external Ports available for which to connectthis configuration of the described embodiment in a USB 2 Hi-Speedconfiguration.

In the Link System 900, as illustrated in FIG. 9, when a USB 3SuperSpeed interconnection is made to a USB Host system via the firstUSB 3 Transmission Line 906A and the first USB 3 Male Type A connector914A, the first USB I/O Device Controller #2 910A may be configured tofulfill data and file transfers between, both to and from, the USBNetwork Bus 218 via the first USB Network Transmission Lines 912A.

In some aspects of the present application, when connected to a USB 3SuperSpeed Host system, the Link System may assign all Host-side andintra-Link or network, system command and management data including nodeaddressing, directional flow, flow control, security, configuration,sync and traffic management, messaging and critical assist and overridefunctions and others, to the first USB I/O Device Controller #1 920A ina separate Communication Link parallel to the Data Link alreadyestablished via the first USB I/O Device Controller #2 910A.

Conveniently, when separate dual and parallel Links are employed, it maybe shown that relatively high data transfer rates may be achieved whenconnecting to USB 3 SuperSpeed Host systems. These relatively high datatransfer rates may be attributed to an exchange of control data andnetwork management data on paths that are separate and distinct from thepath on which the data is exchanged.

In some aspects of the present application, both the first USB I/ODevice Controller #2 910A and the first USB I/O Device Controller #1920A may be deployed as Data Transfer pathways. In this manner, thebandwidth of the first USB I/O Device Controller #2 910A may besupplemented by channeling relatively smaller size transfers to a slowersecondary pathway such as that formed by the first USB I/O DeviceController #1 920A. Additionally or alternatively, deploying thismethod, using both first USB I/O Device Controller #2 910A and USB I/ODevice Controller #1 920A for Data and File Transfers may allow forsimultaneous file transfers in opposite directions.

In the Link System 900, as illustrated in FIG. 9, when a USB 2 Hi-Speedinterconnection is made to a USB Host system via the first USB 3Transmission Line 906A and the first USB 3 Male Type A connector 914A,the first USB I/O Device Controller #2 910A may be configured to fulfilldata and file transfers between, both to and from, the USB Network Bus218 via the first USB Network Transmission Lines 912A.

In some aspects of the present application, when connected to a USB 2Hi-Speed Host system, the Link System may assign all Host-side andintra-Link communications, for example network, system command andmanagement data including node addressing, directional flow, flowcontrol, security, configuration, sync and traffic management, messagingand critical assist and override functions and others, to the first USBI/O Device Controller #1 920A in a separate Communication Link parallelto the Data Link already established via the first USB I/O DeviceController #2 910A.

Conveniently, when separate dual and parallel Links are employed, it maybe shown that relatively high data transfer rates may be achieved whenconnecting to USB 2 Hi-Speed Host systems. These relatively high datatransfer rates may be attributed to an exchange of control data andnetwork management data on paths that are separate and distinct from thepath on which the data is exchanged.

In an example of the embodiment of the invention as a USB Link System,mode selection between USB 3 SuperSpeed and USB 2 Hi-Speed may pertainto the version of the USB Protocol that is being used by the connectedUSB Host system at any given Endpoint, and may be controlled by a higherlevel Application on the USB Host system and by a Link System. The CodeLogic within the Link System may provision capability for the LinkSystem to select modes based on interconnect signal integrity anddegradation level.

Some aspects of the present application may include a method, apparatusand system wherein two or more USB data paths may be established andused simultaneously, in any direction, and that the network and controlpath established between any and all coupled Host systems may beimplemented as a shared resource and may accommodate shared controlmanagement.

FIG. 10 illustrates, in schematic form, the main components and orroutine blocks and or Logic blocks of an Application program 1000 usedto interact with the Link Systems outlined and described previouslyherein, featuring coupling between a first USB Host System 210A (notshown) and a second USB Host 210B (not shown) as per FIG. 2 and FIG. 5.

The Application may host navigation and execution commands provided byinteraction with both the USB Host system and or the User input inoperation of the Link System and coupled USB Host systems. Applicationsoftware involving user interaction at the local level and or at anetwork level, may include a User Interface to provide a means tonavigate and execute pre-programmed processes or routines, involvingsimplistic processes or gestures, such that Data may be transferred fromone coupled USB Host system to another, amongst other desirabletransactions. The Local User Interface 1002, refers to that UserInterface (hereinafter “UI”) pertaining to the USB Host system on whichthe Application may be running and for which there may be a Userinteracting with the Application in real time and in real session. TheUI may include a Data In/Out 1004A data transfer facility or processunit as that which may be exposed to the User as both a reportingfacility and an input facility. The UI may also include Flow Controlfacility and a Data Storage Manager 1008A. The Flow Control facility mayprovide access to viewing and selecting USB Host system Hardware Panelsfor monitoring and selecting Protocol based Endpoints, Ports, Addresses,and Data Handling features. The Data Storage Manager facility mayprovide File and Folder monitoring and maintenance functions, morecommonly known as File Explorer functions whereby Data Storage devicesare listed, and may be selected for retrieving storage capacity and forlisting stored contents in folder and file formats as defined by the OS.

The Application program pertaining to the Link System 1000 of FIG. 10may include a Traffic Manager 1010. The Traffic Manager 1010 is centralto the Application in that all data traversing the USB Network Bus 218(not shown) to and from the coupled USB Host systems, may be requiredthat such traversals induce data traffic on all buses as previouslydescribed herein. For data transversal to be successfully accomplished,an ability to manage timing and path selection, and deselection, may berequired.

In similar functional positioning as that of the Traffic Manager 1010,the Data Exchange 1040 process and the Negotiate Path and DeviceSelection 1020 routines may be the only processes or routines thatdirectly transact across, or traverse, the USB Network Bus 218 (notshown) as Local and Remote references may be considered directionalindicators and may not have logical demarcations. That is to say thatlogic in any of the three routine blocks may be considered as both alogical endpoints of the opposing data and command structures, and as alogical start point to any function or routine in reaction to theopposing endpoints.

The Data Exchange 1040 process may interact directly with the LinkSystem's USB I/O Device Controllers #1 and #2 as previously describedherein. Data within those Memory Blocks 152 and 182 may traverse the USBNetwork Bus under the instruction and direction of the Data Exchangeprocess.

The Negotiate Path and Device Selection 1020 routines may also interactdirectly with the Link System's USB I/O Device Controllers #1 and #2 aspreviously described herein. Selections made by the user and or theApplication may translate into openings or closings of specific ports onthe USB Host systems and may include direct communications with the USBNetwork Controller 100 as described earlier herein.

An Endpoint Manager 1044A routine may be used to determine the necessaryendpoint to target for incoming and outgoing data exchanges as per thedesired user action or in logical reaction to queries from the oppositecoupled USB Host system Application. Logical control sequences areestablished by the Traffic Manager 1010 based on endpoint selectiondetermined by the Local Endpoint Manager 1044A and in synchronizationwith the Remote Endpoint Manager 1044B.

The Data Manager/Converter 1042 routine may establish the format andexchange information of the sending or receiving payloads such thatpayload bits are both counted, aligned, and packaged for transport ineither direction based on the engagement and determination by theTraffic Manager 1010 and respective Endpoint Managers 1044A and 1044B.The Local Data Manger/Converter 1042A may interact with the Remote DataManager/Converter 1042B through interaction with the Traffic Manager1010 Process Logic.

Both the Local Direction Select 1022A and its counterpart the RemoteDirection Select routines may report and react to logic selectionsprocessed by the User input from the Local UI 1002A or the Remote UI1002B, utility if engaged by the user, that may cause or require changeto the Flow Control and Data Storage Manager 1008A and 1008B processesrespectively, and confirmation of Data direction flow and NetworkControl sequences or routines may be synchronized by the Traffic Manager1010, and subsequently may be reported or confirmed by the Applicationto both the engaged logic processes and the Local UI 1002A and or theRemote UI 1002B, if engaged.

In operation of the Link System 1000 of FIG. 10, an applicationexecuting on the first USB Host system 210A (not shown) may detect,sense, negotiate and direct data transfers, Network commands, Controlcommand, and Link System commands to facilitate and synchronize deviceaddressing and data flow through appropriate links. Data flow throughthe first USB Host system 210A (not shown) may involve a device driverexposing available endpoints for data transmission and availableendpoints for network interconnects.

The available endpoints identified may vary depending on the type ofdata transfer via USB protocol to coincide with the desired service modeof the USB Network Interface 212A and 212B (not shown). Example types ofdata transfer include Bulk data transfer, Asynchronous data transfer andIsochronous First-In-First-Out (FIFO) data transfer. Different functionswithin the Application may be directed to different endpoints. Eachendpoint may be selected on the basis of the suitability of the endpointto perform a desired function. Similarly, data traffic may be directedto an endpoint that is suited to an identified data speed when couplingdifferent versions of USB Hosts.

The Local Endpoint Manager 1044A may enable selection of, and switchingto, various endpoints to meet requirements specified by an Application.The Local Endpoint Manager 1044A may also enable, engage or require theLocal Data In/Out Transfer process 1004A of the Local USB Host system210A (not shown).

The Local Data Manager 1042A may be engaged by an Application viarequisite declaration of required space, file name(s), directory, filetype(s) and supplemental processes, such as byte count, checksum, andothers. Direct communication between the Local Data Manager 1042A andthe Traffic Manager 1010 may assist to allow for relatively accuratedata transfers and relatively higher levels of security. In this way,data transfers may be seen as highly efficient and a reduction may berealized in collisions and transfer resends.

In operation, activities at the Data Exchange 1040 may align to theneeds of the Traffic Manager 1010 to support various modes of operationto allow for relatively high data transfer speed, relatively highbandwidth, relatively high security and relatively high data integrityfor the attached or coupled USB Host systems 210A and 210B (not shown)respectively.

In operation, the Traffic Manager 1010 may seek information for link orpathway determination for efficient data transfer. Devices, deviceendpoints and data paths may be taken into account with respect to DataFlow direction, network and control messaging, and process reporting toan Application and to a USB Network Interface.

Also in operation, the Negotiate Path and Device Selection Unit 1020 mayexecute logic when such information for link or pathway determination issought by the Traffic Manager 1010 or when triggered by the Local and orRemote Direction Select 1022A and 1022B processes respectfully, and orby the Local and or Remote Flow Control and Data Storage Manager 1008Aand 1008B processes respectively.

The Local Direction Select 1022A and the Local Flow Control and DataStorage Manager 1008A may execute processes within a Local USB NetworkInterface 212A in conjunction with an Application's requirements andevents that may be triggered by the Local USB Host system 210A (notshown) and Link System 1000 logic. The Local Operating System 234A (notshown) and a Local Application 240A (not shown) may execute at the LocalUSB Host system 210A (not shown) and may interact to indicaterequirements to the Local Flow Control and Data Storage Manager 1008Aaccessed via the Application 240A and Local device drivers, such thateach communicates directly with the Local USB Network Interface 212A(not shown) logic in collaboration with the Remote USB Network Interface212B (not shown) logic across the Network and Control Management Bus136A and 136B (not shown) respectfully. The same could be said withrespect to processes triggered or executed on both the Local and or theRemote sides or counterparts of those referenced above.

1. A network host, comprising: a host processing unit, the hostprocessing unit capable of logical processing and address processing andprovided to establish a network and control management module foraddressing and network switching, the host processing unit including: adata bridging bus input/output transceiver for operatively connectingthe host processing unit to a data bridging bus for sending datacommunications to the data bridging bus or accessing data communicationsfrom the data bridging bus, and a control bridging bus input/outputtransceiver for operatively connecting the host processing unit to acontrol bridging bus for sending or accessing control communications onthe control bridging bus, and wherein the host processing unit isconfigured to provide data communications to the data bridging bus oraccess data communications on the data bridging bus as coordinated witha further processing unit over the control bridging bus.
 2. The networkhost of claim 1, wherein the host processing unit and the furtherprocessing unit are central processing units.
 3. The network host ofclaim 1, wherein the data communications are unpackaged datacommunications provided over an electrical, optical or wireless medium.4. The network host of claim 1, wherein the control communications arecommunicated using either structured or unstructured communications. 5.The network host of claim 4, wherein the control communications arecommunicated using a system bus protocol.
 6. The network host of claim1, wherein the host processing unit includes a further data bridging businput/output for operatively connecting the host processing unit to afurther data bridging bus for sending data communications to the furtherdata bridging bus or accessing data communications from the further databridging bus.
 7. The network host of claim 1, wherein the controlbridging bus input/output transceiver is provided to establishelectrical, optical or wireless communications.
 8. The network host ofclaim 1, wherein the host processing unit is configured to supportnetworked communications for a dedicated function or resource.
 9. Thenetwork host of claim 8, wherein the dedicated function or resource isat least one of memory, graphics, and encryption.
 10. A network system,comprising: a data bridging bus; a control bridging bus; a first networkhost including a first processing unit, the first processing unitcapable of logical processing and address processing and provided toestablish a first network and control management module, the firstprocessing unit including: a first data bridging bus input/outputtransceiver for operatively connecting the first processing unit to thedata bridging bus for providing data communications to the data bridgingbus or accessing data communications from the data bridging bus, and afirst control bridging bus input/output transceiver for operativelyconnecting the first processing unit to the control bridging bus; asecond network host including a second processing unit, the secondprocessing unit capable of logical processing and address processing andprovided to establish a second network and control management module,the second processing unit including: a second data bridging businput/output transceiver for operatively connecting the secondprocessing unit to the data bridging bus for providing datacommunications to the data bridging bus or accessing data communicationsfrom the data bridging bus, and a second control bridging businput/output transceiver for operatively connecting the secondprocessing unit to the control bridging bus; and a third network hostincluding a third processing unit, the third processing unit capable oflogical processing and address processing and provided to establish athird network and control management module, the third processing unitincluding: a third data bridging bus input/output transceiver foroperatively connecting the third processing unit to the data bridgingbus for providing data communications to the data bridging bus oraccessing data communications from the data bridging bus, and a thirdcontrol bridging bus input/output transceiver for operatively connectingthe third processing unit to the control bridging bus; wherein thefirst, second, and third network hosts are configured to provide datacommunications to the data bridging bus or access data communications onthe data bridging bus as coordinated between themselves over the controlbridging bus.
 11. The network system of claim 10, wherein the controlbridging bus is established electrically, optically or wirelessly.
 12. Asystem for transferring data between a first host computer and a secondhost computer, comprising: a first host computer capable of sending andreceiving data and control information; a second host computer capableof sending and receiving data and control information; a bridgingapparatus including at least two input/output transfer devices arrangedin bridge formation providing for an exchange of data over a shared bus;and wherein the first and second hosts establish the effect of a dataconnection through the bridging apparatus, and transfer of data betweenthe host computers across the bridging apparatus is determined jointlyby the host computers with the first host computer providing data to thebridging apparatus and the second host computer retrieving data from thebridging apparatus such that neither host computer controls the datawhile traversing the shared bus.
 13. The system of claim 12, wherein thefirst host computer and the second host computer each comprise installedsoftware, which, when executed, establishes a network between the firsthost computer and the second host computer and provides for the transferof data and control information over the bridging apparatus.
 14. Thesystem of claim 13, wherein the installed software establishes a networkand control manager adapted to create a transient interconnectionbetween the first host computer and the second host computer and toestablish addressing and a data manager adapted to transact data andfile transfers between the first host computer and the second hostcomputer.
 15. The system of claim 13, further comprising a third andsubsequent host computer.
 16. A method for transferring data between afirst host computer and a second host computer comprising: establishinga networking bus; communicatively coupling a first host computer to thenetworking bus; communicatively coupling a second host computer to thenetworking bus; establishing a virtual control link between the firsthost computer and the second host computer through the networking bus;establishing a data link between the first host computer and the secondhost computer through the networking bus; and transferring data from thefirst host computer to the second host computer by communicating thedata over the networking bus to the second host computer.
 17. The methodof claim 16, wherein the data is communicated over the data link usingUSB protocol.
 18. The method of claim 16, further comprising the firsthost computer using a resource of the second host computer over thenetwork by logical direct access.
 19. The method of claim 18, whereinthe resource comprises a peripheral device.
 20. The method of claim 18,wherein the resource comprises a host resource.